Release notes

TIP: Looking for release notes for all Axiom products, including current previous versions? Click here.

NOTE: Download a PDF version of the release notes here.

New features and enhancements in 2023.3

See What's New.

About the release notes

Syntellis is pleased to announce the 2023.3 release of Axiom Budgeting and Performance Reporting. Each product release provides new features, enhancements, and configuration options. Many of these features and enhancements are a direct result of your feedback and suggestions.

The purpose of these release notes is to provide you with the following:

  • High-level descriptions of new features
  • Information to know before upgrading
  • Steps for preparing for and scheduling your upgrade
  • List of fixed issues

Prior to upgrading, review the Axiom 2023.2 Release Notes and the release notes for each product that is licensed by your organization.

What to know before upgrading

IMPORTANT: You must apply the latest Axiom upgrade before applying any 2023.3 Axiom product upgrades. Axiom upgrades are backward compatible so you can upgrade different products at different times, but you must upgrade to Axiom 2023.2 before the first product upgrade. Refer to the Axiom Release Notes for consideration before upgrading.

When upgrading to the 2023.3 version of Axiom Budgeting and Performance Reporting, note the following:

  • You can replace Syntellis reports. Any report that you created or saved under a different name remains unchanged. Revised reports are available in Document History.
  • Any Syntellis report that was moved to a new location is automatically returned to its original location.
  • Syntellis product templates and calculation method libraries are replaced.
  • Product task panes are replaced.
  • Process definitions are not replaced.
  • Driver files are replaced.
  • Security roles and subsystems are reset to their configured settings. Your user security exceptions remain intact.
  • Specific items that are configured as part of your company or organization’s implementation such as imports, exports, driver files, and process management files, remain unchanged. Any required modifications to these areas are covered in the release notes.

  • Shared tables might have any of the following changes:

    • Columns reordered

    • New columns added

    • Old columns removed (rare)

  • If you copy and paste into or from Axiom tables, please review the column order of those tables after upgrading to assess the impact to your internal processes.

Prepare and schedule upgrades

Summary of the upgrade process:

  1. Review product release notes – Review this document to become familiar with the new features and functionality.
  2. Schedule an installation date – Submit a request to your organization’s Axiom System Administrator or contact Support by creating a support case to request a Preferred Upgrade Window:

    • Log in to Syntellis Central.

    • Click Support Cases.

    • Click Schedule an upgrade.

    • Enter your Preferred Upgrade Window information.

    • Click Submit.

  3. Complete manual configuration updates – After installing the upgrade, review any manual setup steps to enable features for this version.

Get help and training

Syntellis provides world-class resources directly within the Axiom system. Axiom Help provides topics, release notes, webinar/training announcements, and videos to guide you through managing your system.

To access these resources, click Online Help from the Main or Admin tabs, and then select the product. Axiom Help opens in a new browser. The online help opens only for products you are licensed to use.

Syntellis Central

  • Search help across all Axiom products.

  • Access tips, tricks, and best practices in our knowledge base.

  • Find training and certification content, including on-demand, video, webinars, labs, and instructor-led courses.

  • Ask a question in the peer-to-peer Syntellis Community.

  • Submit a Support issue, find suggested content, and manage any outstanding issues directly with Support.

Issues fixed in 2023.3.3

The following table lists the resolutions for issues addressed in 2023.3.3, released October 9, 2023:

Budgeting: templates, plan files, and drivers

Issue Description Description
Benefits rows on Initiative tab are not shown as approved and not appearing on Summary tab. [#73976]

Summary: When new initiatives with Benefit account details were added to the budget plan file, the Benefit account detail was saved only to the BUD20XX_Detail table. The data was not saved to the BUD20XX table after the initiative was approved.

This issue affects the following calculation methods:

  • Add Salary

  • Salaries

  • Add Deductions

  • Deductions

  • Add Detail Benefits w Percent

Resolution: For these five calculation methods, the formulas were changed in columns Z:AK to reference the corresponding monthly values in columns I:T, multiplied by the anchored value in column AL. The value in AL is 1 when initiative is "Approved" and 0 (zero) when the initiative is excluded.

Issues fixed in 2023.3

The following table lists the resolutions for issues addressed in 2023.3, released August 28, 2023:

Budgeting: templates, plan files, and drivers

Issue Description Description
BP Update Lump Sum Global Reference in 02 Labor Configuration Driver [#59169]

Summary: The PayType selection did not reference the last saved update in row 89 in the Global section of the 02 Budget Labor Configuration Driver.

Resolution: Updated the calculation method formula to the following:

=IF(OR(BA89="",BA89=0),"NotUsed",BA89)
Budget Provider Config Driver 29 - Monthly FTE Spread for Providers inputs not responding to Monthly Default Spread for Providers Source dropdown. [#59164]

Summary: When Budget Config Driver was selected in the Monthly Default Spread for Provider row, the hour values did not link to the inputs made in the 02 Budget Labor Configuration driver.

Resolution: Updated the hour links to pull from the 02 Budget Labor Configuration driver when Budget Config Driver is selected on the dropdown.

 
BP Budget Configuration driver - BudgetGroup refresh variable not filtering displayed output [#59180]

Summary: On the Budget Configuration driver, the BudgetGroup refresh variable was not recognized.

Resolution: Updated the query filter references from E19 to A29 to accept the BudgetGroup refresh variable.
Case Number 00488834 - Provider plan file Drivers tab AQ. [#59178]

Summary: With the index formula in columns HP to IB in the Global Provider row, if the provider was not found in column B on the Drivers tab, column HN = 0. However, the row of the formula was still used in the index formula, which caused an improper lookup.

Resolution: Integrated conditional logic to default to 0 (zero) when the row lookup value is 0 (column HN):

@IF($HN213=0,0,INDEX(Drivers!$C:$Q,$HN213,HP$27))

BP Stat_Rev tab - Multiple CMs - Incorrect determination for Revenue Adjustments driver prioritized exceptions code. [#59183]

Summary: An incorrect determination for the Revenue Adjustments driver prioritized the exceptions code.

Resolution: Added a new Fixed Revenue calculation method on the Stat_Rev tab.
PFB-09144 - Adding new jobcode is not picking up LaborLimit Midpoint rate as start rate. [#59195]

Summary: When a new jobcode was inserted in the JOBCODE tab, the Start Rate did not pick up the Midpoint rate in the LaborLimits driver.

Resolution: Added the following to the reference driver instead of defaulting to $0:

GetData(Variables!$P$55&".Mid","code='"&A397&"'")

PFB-09037 - Need to round SUM() function in column Z of ProviderDetail16 row in calc method. [#59202]

Summary: An error occurred when a small decimal value (for example, .0000000000001) was entered in Column CY of the ProviderDetail16 row.

Resolution: Applied a function to round the value to six decimal places.

 

Case Number 00507639 - Target budget adjustment not saving as expected on Employee tab. [#59160]

Summary: For departments budgeting by employee, the target adjustments from the budget plan files did not save the dollars and hours from the Employee tab to the database table. This issue caused various reports to show different budget values for salaries.

Resolution: Copied hour and dollar cell references from FE109:GE109 to FE107:GE107.
Case Number 00509016 - Staffing tab: The Input Monthly calc method paytypes, the NYB monthly spread columns producing incorrect results. [#60823]

Summary: The NYB (Next Year's Budget) monthly spread columns referenced columns GH:GS. These columns then referenced non-value columns K:L instead of the YTD and Projected columns of O:P.

Resolution: Changed cell GH[row] formula in the Input_Monthly calc method from

=SUM(K[row]:L[row])

to

=SUM(O[row]:P[row])

Performance Reporting

Issue Description Description
Case Number 00488132 - Flex Budget Calculator Primary Table. [#58545]

Summary: An account with a flex percent of 100% in the ACCT (Account) dimension returned 0% in column Q of the Flex Calculator.

Resolution: Updated the cell reference for AQ1 to the Bud table name instead of the Act table name.
Case Number 00492700 - Executive Monthly Package missing entity filter for refresh variable. [#58546 ]

Summary: The Executive Monthly Package report did not apply the Entity refresh variable filter.

Resolution: Modified the primary filter reference for all sheets to include Entity as a refresh variable.